home *** CD-ROM | disk | FTP | other *** search
- From: thp@cs.ucr.edu (Tom Payne)
- Message-ID: <4dekiv$22h@galaxy.ucr.edu>
- X-Original-Date: 15 Jan 1996 22:30:55 GMT
- Path: in1.uu.net!bounce-back
- Date: 16 Jan 96 10:35:45 GMT
- Approved: fjh@cs.mu.oz.au
- Return-Path: <daemon@meeker.UCAR.EDU>
- Newsgroups: comp.std.c++
- Subject: Re: Throwing an exception from within a signal handler
- Organization: University of California, Riverside Department of Computer Science
- References: <4cpmh0$ltf@natasha.rmii.com> <Etay_Bogner-0901961008510001@metay.stil.scitex.com> <9601003.29971@mulga.cs.mu.OZ.AU>
- X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
- X-Auth: PGPMoose V1.1 PGP comp.std.c++
- iQBFAgUBMPt/kOEDnX0m9pzZAQFHEQF/UR6fGo4YDEpn3eIqid3ibXQO0EDE+v+U
- 0QsGBXVvjgO4I4k2cSXfZlqHOIvLaRtl
- =yxeV
-
- Fergus Henderson (fjh@munta.cs.mu.OZ.AU) wrote:
- :
- : >In article <4cpmh0$ltf@natasha.rmii.com>, jtc@rmii.com (Jim Cochrane) wrote:
-
- : >>>
- : >>> Does the proposed ANSI standard say anything about throwing an exception
- : >>> from within a signal handler?
- :
- : No.
- :
- : >>> Is the resulting behavior safe and
- : >>> well-defined, or is it undefined or implementation-dependent?
- :
- : Because the draft standard doesn't say anything about it,
- : I guess it is implicitly undefined behaviour.
- :
- [...]
- :
- : I think the issue of whether the standard says anything about *Foo* is
- : generally appropriate to comp.std.c++, even if the answer is "No.", and
- : the resulting discussion rather short.
-
- Implicit in a qestion of what the Standard says are the related
- questions of what it should say and why --- why shouldn't signal
- handlers be allowed to throw exceptions? (The question seems both
- interesting and appropriate.)
-
- Tom Payne (thp@cs.ucr.edu)
- ---
- [ comp.std.c++ is moderated. Submission address: std-c++@ncar.ucar.edu.
- Contact address: std-c++-request@ncar.ucar.edu. The moderation policy
- is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]
-